home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
romdoor.zip
/
ROMDOOR.DOC
< prev
next >
Wrap
Text File
|
1991-02-11
|
11KB
|
275 lines
* CD ROM LOCAL/REMOTE DOOR *
Helix Software Foundation
James H. Snowden
FidoNet 1:325/123
BBS: 802-899-4988
* What it is *
This program allows the user to search, unpack specified groups of files,
typically on a CD-ROM. It handles global and group searching for
keywords. ANSI and ASCII modes are supported. Both remote and
local use is supported. Remote use is intended for sysops who
want to let users access a CD-ROM they own.
ANSI/ASCII Support
The door is told whether a user wants ANSI via the command line
switch -A<n>. If <n> is 1, all system text files that are
displayed (help files, intro, etc) a .ANS extension will be
searched for first. If a .ANS file is not found then the door
will look for a .ASC file and display it. If the user does not
have ANSI, .ASC files will always be displayed.
Transfering Files
The main impetus for writing this door was due to the fact that
I did not want to add umpteen-million groups of files to my BBS
but still wanted to use the BBS download capabilities, download
ratio checking, security, etc.
The solution was to have the user choose what files he/she wants
off of the CD-ROM, and have them transferred into ONE or more CD-ROM
Transfer areas in the BBS for later downloading. This adds one step
for the user to get CD-ROM files, but the users on my board seem
to like the doors... though nothing is ever perfect, and I am
always looking for ways to improve the door.
Flexibility
This program allows for people to use pre-created modules to
access CD-ROMS and create their own. Creating a new module is as
simple as creating a few text files... no programming involved.
It also allows one to access and search multiple CD-ROM's...
It is simple as creating combined lists for files and organizing
them... see Installation below for more details.
Local/Remote Use
The program acts a little differently for local and remote use.
For local use, there is an added option, unpack cd file to a
specified path. The transfer option is also slightly different
for local use, a path is entered where remote users have no
choice, it is specified in the config file instead for BBS
security.
It also watches remote users time, gives a warning at five minutes and
bumps him/her back into the BBS a two minutes.
* Installation *
There is one big factor that will determine how this thing is installed.
ROMDOOR was developed to allow people to create a "front end" to
search thru and extract files on a shareware type CD-ROM. The factor
is whether you are creating a new CD door... or you are using one
someone else has already created. I call each set of these CD-ROM specific
data files a "module". If you have a module for the CD you want to access,
there should be virtually no installation or messing with the config
files unless you want to change how it was done.
- Make sure ansi.sys or equivalent is in the config.sys file, for local
use.
Quick Install for those using a precreated module
o Make a directory for the door
o Uncompress the files of the module into that directory
o Uncompress the files of romdoor into that directory
Creating a new module
o Make a subdirectory for the door
o Create description file for each area (should be supplied with CD)
o Create database file list for romcopy (see romcopy.doc)
o Create catalog file
o Create config file
o Create/Modify other ansi/ascii support files
o Create the batch file that BBS will invoke to start the door
(see Things NOT covered by the Door below)
o Create a batch file for you (and possibly others) to run
locally
Please, if you create a decent module, upload it to my BBS so I
can make it availible FREQable for all...
Catalog File
The catalog file is simply a list of the different file areas
availible. Give it any format you like, as long as the areas
are labeled 1-whatever and are in the same order as the config
file AREA commands (see AREA below). The system supports
ANSI/ASCII versions of the file, and the filename is specified
in the config file by the CATALOG statement.
Config File (Default of ANSIDOOR.CFG)
The configuration file contains setup info which differs from
one BBS to the next. The following items are need to be in the
config file:
XFER_DEST D:\RA\CARRS
XFER_DESC D:\RA\CARRS\FILES.BBS
BBS_NAME "The Data Dungeon!"
AREA f:\001A\001.cat Communications
AREA 002.cat Games
DECOMP_COMMAND "pkunzip -d "
CATALOG catalog
INTRO carrs
DEF_EXT .zip
CDROM_NAME "CARRS Bonanza"
An explanation of each follows:
XFER_DEST: For Remote mode, this is the directory where users will
transfer files from the CD to.
XFER_DESC: This is the file description list for the transfer directory.
AREA: This allocates a new area for the CD. The first parm is the
path to the description list for that area, and the
rest of the line is the name of the area. There should
be one of these statements for every file area you want to
have.
*** TIP: You don't have to use the file "areas" that are
on the CD. If you don't like how things are arranged
on the CD, split up the description files how you
would like to see it done. There are no ties to the
different areas, since ROMCOPY does not need to know where
the file to be transferred is coming from. For example,
if there are a bunch of BASIC game descriptions in the
Games directory of your cd rom, you could make a new area
called BASIC games, and split the games file directory
into two description files on your hard drive.
DECOMP_COMMAND: The command to decompress a file. The example given
is pkzip, but you will want to use whatever is appropriate
for that CD.
CATALOG: The name of the catalog file. If no extension is given, the
door will look for <name>.ans if the person has ANSI,
and then <name>.asc. This is displayed when the user
needs/wants to change file areas.
INTRO: The name of the intro file. If no extension is given, the
door will look for <name>.ans if the person has ANSI,
and then <name>.asc. This file is displayed when the door
is first called.
CDROM_NAME: Yep, you guessed it. Surround the name in quotes.
BBS_NAME: Yep, you guessed it. Surround the name in quotes.
Comment lines are allowed in the config file and are identified
with a semicolon in the first column.
* Command Line Switches *
-A<n> where <n> is 0 for ASCII mode and 1 for ANSI mode
-N<n> where <n> is the users first name
-T<n> where <n> is the amount of time left on system
-R<n> where <n> is 0 for LOCAL (default) mode and 1 for REMOTE mode
-C<n> where <n> is the name of the config file to use, if none is
specified, ANSIDOOR.CFG is used as a default.
* TEXT Support Files *
HELP.ANS/ASC This file is displayed when the user asks for help from
the main menu.
FILESAVE.ANS/ASC Displayed when user has transferred a file to the
BBS for later download in the current door session.
* Things NOT covered by the Door *
CD Watchdogging... Most want their system to recover from a
user hanging up, and this simply reboots the BBS if the carrier detect
signal from the modem desists. I did not write it in to the door
due to the fact that today's FOSSIL's usally have it built in. I
am trying BNU at the moment, and it has worked flawlessly.
Output/Input... Video output and keyboard input is done through the
standard channels. This works nicely for running it locally, but
when you want to allow a remote user to run it, all input/output
needs to be routed though the com port... there are two ways
to do this. The first way is to use the CTTY COM1 directive
before the execution of the door, and the CTTY CON after the
door executes. I use a device driver called GATEWAY that allows
for simultaneous input/output locally AND through the COM port.
Therefore, my batch file that starts the door looks like this:
@echo off
break off
bnu /W=0+ ; Turn Watchdogging ON
ctty gate1 ; Redirect input/output
d:
cd \ra\rbbsbox ; Switch to the doors directory
romdoor -C %1 %2 %3 %4 %5 %6 ; Start the DOOR
ctty con ; Redirect input/output back
bnu /W=0- ; Turn Watchdogging OFF
cd \ra ; Switch back to the BBS dir
* Future Enhancements *
There are a TON of things I would like to add to this thing, but like
all projects, if I can't get the funding through my users, I can't
justify putting much into the project, so please register! Enhancements
I would like to see in this thing include:
o Chat while in remote mode
o Direct downloading from within door
o Transfer times for files
If you think of something, let me know!
* Registering *
Single site registration...
You can use this door to drive a 100 CD's, as long as it is on one
machine. Please register one copy per machine @ 15$ a copy.
Registering provides me with a good reason to work on the project, and
provides you with the following:
o The latest version of ROMDOOR
o No pause at the beginning of each run
o One FREE update
o A list of FREQable modules for ROMDOOR from the HSF BBS
o A catalog of HSF products
o Better karma, peace of mind??
CD ROM Producers...
Please contact me! I am ALWAYS willing to make a deal with people
creating the latest in CD technologies.
* License Information *
There is no warranty, written or implied. Helix Software
Foundataion is not responsible for any damage in the use or misuse
of this software and is distributed in an AS-IS state. This does
NOT mean that I am uninterested in the enhancements you would like
to see, please send them to me via FidoNet or via US Mail...
James Snowden
PO Box 693
Essex Junction, VT 05453
The Data Dungeon! BBS
1:325/123
1.5 Gigabytes of files online
1-802-899-5088
14.4 HST/V32